Memory with Alternative Command Interfaces

ABSTRACT

A memory device or module selects between alternative command ports. Memory systems with memory modules incorporating such memory devices support point-to-point connectivity and efficient interconnect usage for different numbers of modules. The memory devices and modules can be of programmable data widths. Devices on the same module can be configured select different command ports to facilitate memory threading. Modules can likewise be configured to select different command ports for the same purpose.

BACKGROUND

Processing units (PUs) execute instructions to read, manipulate, and write data. Both the instructions and data are commonly stored in a separate memory, which is coupled to the PU via a communication channel. In a common example, a personal computer (PC) normally includes a central processing unit (CPU) coupled to a quantity of dynamic, random-access memory (DRAM) via a channel called a “memory bus.”

The speed at which a PU can process instructions depends in part on how fast the memory is able to read and write instructions and data, which in turn depends in part on the speed with which signals can be communicated over the memory bus. Faster computers ideally employ faster memory buses, so a considerable amount of resources have been expended improving the speed performance of memory buses.

Memory buses are commonly “multi-drop,” which means that a number of memory devices can share the same channel. Multi-drop buses are desirable because they allow manufactures and users the flexibility to provide different types and amounts of memory. However, multi-drop buses tend to degrade signals, and thus reduce speed performance. An alternative to multi-drop buses, so-called “point-to-point” connections, directly connect the PU to the one or more memories, and thus avoid signal degradation that results from bus sharing. One problem with these systems is that point-to-point connection resources are wasted unless the memory system has the maximum number of memories. In a topology that supports two memory modules, for example, half the point-to-point interconnects would be wasted in a one-module configuration.

The assignee of the instant application developed “Dynamic Point-to-Point (DPP)” memory-bus topologies that allow manufacturers and computer users the flexibility to provide different numbers of memory modules in a manner similar to multi-drop buses but without the wasted connection resources that can result in conventional point-to-point topologies. In DPP topologies, the same number of point-to-point connections can be used for different numbers of memories. Most memories and memory systems do not support DPP connectivity, and thus lack the benefits of these systems. There is therefore a need for simple and inexpensive means for speeding the adoption of this important technology.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an embodiment of a memory device 100 having circuitry to support alternative command interfaces and variable data widths.

FIG. 2 depicts a memory system 200 in which a single memory module 205 populated with eight memory devices 100 of the type detailed in connection with FIG. 1 is connected to a processing unit (PU) 210 via a sixty-four-bit data interconnect 215A/B and a command interconnect 220 and a shorting module 225.

FIG. 3 depicts a memory system 300 similar to system 200 of FIG. 2 but with two memory modules 205A and 205B populating connectors 230.

FIG. 4 is a plan view of a memory system 400 in accordance with one embodiment similar to systems 200 and 300 of FIGS. 2 and 3.

FIG. 5 depicts a memory module 500 in accordance with another embodiment.

The figures are illustrations by way of example, and not by way of limitation. Like reference numerals in the figures refer to similar elements.

DETAILED DESCRIPTION

FIG. 1 depicts an embodiment of a memory device 100 having circuitry to support alternative command interfaces and variable data widths. This combination of features supports DPP memory topologies with little or no added complexity to the memory device. In the particular embodiment shown, and other embodiments disclosed herein, memory device 100 is a dynamic random access memory (DRAM) device that includes, among its component circuit blocks, a command multiplexer 105, control logic 110, and a DRAM core 115. Mode memory 120, in this instance a register coupled to control logic 110, stores a value that determines which of two command ports CA0 and CA1 is used to receive memory commands (e.g., read and write commands), and whether DRAM core 115 communicates four-bit-wide data or eight-bit-wide data.

Command multiplexer 105 directs commands received on one of two command ports CA0 and CA1 to a command decoder 125 within controller logic 110. Control logic 110 responds to decoded requests by issuing appropriately timed bank, row, and column address signals Bank/Row and Bank/Col, and control signals Ctr10 and Ctr11, to core 115.

Core 115 includes row and column address decoders 130 and 135, K memory banks 140[K-1:0], and a data interface with two four-bit read/write queues 145 and 150 that communicate data via respective ports DQ[3:0] and DQ[7:4]. Each bank 140, in turn, includes J sub-banks 155[J-1:0], each populated with rows and columns of memory cells (not shown), and a column multiplexer 160.

Control logic 110 and DRAM core 115 support memory functionality that is well understood by those of skill in the art. Briefly, control logic 110 decodes incoming commands and issues control and timing signals to core 115 to carry out the requested operation. For example, control logic 110 can send row address, bank address and control information to row decoder 130 in response to a row-activation command, and column address, bank address and control information to column decoder 135 and control signals to data queues 145 and 150 in response to a column-access command. Data can be read from or written to core 115 via one or both of ports DQ[3:0] and DQ[7:4] responsive to these signals.

DRAM core 115 is data-width programmable, responsive to the value stored in register 120 in this example, to communicate either four-bit-wide data on either one of ports DQ[3:0] and DQ[7:4], or eight-bit-wide data simultaneously on both. In the eight-bit configuration, control logic 110 enables both of queues 145 and 150 and the addressing provided to column decoder 135 causes column multiplexer 160 to communicate eight bits in parallel from two or more sub-banks. In the four-bit configuration, control logic 110 enables one of queues 145 and 150, and halves the number of sub-banks used for data access. Halving the number of sub-banks reduces the power required for, e.g., row activation, and consequently reduces power consumption. Other embodiments support more and different data widths.

Register 120 also controls command multiplexer 105 to determine whether commands are directed to decoder 125 via command interface CA from command port CA0 or command port CA1. As detailed below, the provision for a selection between multiple command ports supports DPP connections with minimal added circuit complexity. Memory systems populated with memory devices 100 thus provide the performance of point-to-point connections without sacrificing the flexibility of multi-drop bus architectures.

Register 120 can be loaded at start-up to store a value indicative of data width and the selected command port. Register 120 can be implemented using a programmable configuration register or other volatile circuitry, or by non-volatile circuitry such as a one-time-programmable elements (e.g., fuse-controlled logic), floating-gate devices or any other nonvolatile storage. In other embodiments memory width and one of the command ports can be selected differently, such as by the use of a control pin or other types of configuration interfaces.

FIG. 2 depicts a memory system 200 in which a single memory module 205 populated with eight memory devices 100 of the type detailed in connection with FIG. 1 is connected to a processing unit (PU) 210 via a sixty-four-bit data interconnect 215A/B, a command interconnect 220, and a shorting module 225. PU 210 may be, e.g., a memory controller or a central processing unit that supports memory-control functionality. Memory module 205 and shorting module 225 are installed in respective module connectors 230 so that module pads 235 establish electrical connections to connector pads 240, and consequently to interconnects 215 and 220.

The mode register 120 in each memory 100 is programmed such that queues 145 and 150 (FIG. 1), functionally depicted in FIG. 2 as a multiplexer and pass gate, communicate eight-bit-wide data DQ[7:0]. In the example at the upper left, register 120 is set to receive commands via interface CA1 and to communicate data on both four-bit data ports DQ[3:0] and DQ[7:4]. Port DQ[7:4] is connected directly to a module data port MDQ[7:4] on PU 210 via four signal conductors of data interconnect 215A. Port DQ[3:0] is also connected to a module data port MDQ[3:0] on PU 210 via four signal conductors within interconnect 215A, but this connection is made via jumpers 245 on shorting module 225. The remaining seven memory devices 100 are likewise connected to PU 210 via corresponding collections of conductors.

PU 210 has four command ports, each of which directs commands to two of the eight available memory devices 100. Registers 120 in four of the eight memory devices 100 are programmed such that their respective command multiplexer 105 selects command port CA1; the remaining four memory device 100 are programmed to receive commands via port CA0. Programming can be accomplished using a mode-register command directed to a default command address on each memory device, with a mode register value for each memory device conveyed on subset of the module data ports. Each memory device could thus configure itself responsive to an appropriate register value and thereafter communicate commands and data on the selected connection resources. In other embodiments the command and data signal paths can be selected using other means, such as by programming fusable, flashable, or electrically programmable registers, or by selecting appropriate jumper settings.

In the example of FIG. 2, darkened and hollow squares on the periphery of each memory device 100 indicate active and inactive ports, respectively. Interfaces MCA0 and MCA2 connect to respective command ports CA1 and CA0 of the leftmost four memory devices 100; interfaces MCA1 and MCA3 connect to respective command ports CA1 and CA0 of the rightmost four memory devices 100. The connections for interfaces MCA0 and MCA1 are made via jumpers 245 on shorting module 225. The single installed module 205 thus provides 64-bit data responsive to commands on four available module command ports 250.

The provision of multiple command interfaces MCA[3:0] allows PU 210 to independently control fractions of memory devices 100, sets of two in this example. This technique, sometimes referred to as “threading,” allows PU 210 to divide memory interconnect 215A/B into four sub-channels that convey relatively narrow memory “threads.” Support for memory threading allows PU 210 to reduce access granularity where appropriate, and consequently reduce power consumption for memory accesses narrower than 64-bits.

FIG. 3 depicts a memory system 300 similar to system 200 of FIG. 2 but with two memory modules 205A and 205B populating connectors 230. Each of modules 205A and 205B is identical to module 200 of FIG. 2, but for the configuration of the constituent memory devices 100. PU 210 is omitted for ease of illustration.

Absent shorting module 225, module command interfaces MCA0 and MCA1 do not connect to module 205A; rather, traces on module 205B connect each of command interfaces MCA0 and MCA1 to a respective half of memory devices 100 on module 205B via their device command ports CA0. Every memory device 100 on both modules 205A and 205B is configured to be four-bits wide to communicate four-bit-wide data via respective module data-bus lines responsive to commands on their respective command port CA0. The two half-width modules 205A and 205B provide twice the storage space of one module.

As in the single-module example of FIG. 2, the data and command interfaces from the processing unit are fully utilized, the four command interfaces MCA[3:0] facilitate independent control of four subsets of memory devices 100, and memory interconnect 215A/B is divided into four sub-channels that convey relatively narrow memory “threads.” The processing unit, connectors 230, and the board traces that extend between them are not modified to facilitate this extension. Further, the flexibility to provide either one or two modules comes without the need for multiple drops on the system data interface (command is multi-drop on each module).

FIG. 4 is a plan view of a memory system 400 in accordance with one embodiment similar to systems 200 and 300 of FIGS. 2 and 3, with like-identified elements being the same or similar. Circuit details are omitted so as not to obscure the signal interconnect system provided by command and data interconnects 220 and 215 and connectors 230. This system utilizes point-to-point signaling in a way that permits maximum utilization of existing signal lines while accommodating different numbers of memory modules. Connectors 230, processing unit 210, and the interconnecting traces that pass data and command signals are on and within a printed-circuit board (PCB), such as a computer motherboard or system backplane. Connectors 230 are, e.g., memory-module sockets that receive and support installable/removable memory modules 205. As noted previously, one of connectors 230 can receive a shorting module that forwards signals between processing unit 210 and the other connector 230. A shorting connector can be used in lieu of a shorting module in other embodiments. A shorting connector might establish jumper connections 405 absent an installed module, for example. Module connectivity can also be modified using, e.g., other forms of programmable interfaces on or integrated with the PCB.

While the foregoing embodiments support either two or four threads per module, other embodiments can support other more or different combinations. With reference to the single- or dual-module configurations of FIGS. 2 and 3, for example, similar embodiments can include additional connectors and more complex interface routing to support higher numbers of modules while maintaining point-to-point connectivity. In an embodiment in which each memory device can be configured to have a width of two, for example, each of four modules can be configured to communicate 16-bit data responsive to one of command interfaces MCA[3:0]. The two half-width modules 205A and 205B provide twice the storage space of one module. In such embodiments the four command interfaces MCA[3:0] facilitate independent control of four subsets of memory devices, as in the prior examples, to divide the interconnect into four sub-channels that convey module threads.

FIG. 5 depicts a memory module 500 in accordance with another embodiment. Module 500 includes eight variable-width memory devices 505 and a configurable command buffer 510. Memory devices 505 lack command multiplexer 105, but module 500 nevertheless provides command-bus routing in support of DPP connectivity in the manner detailed above.

Each memory device 505 may be as detailed in connection FIG. 1 but for the omission of command multiplexer 105. That is, each memory device 505 has but one command port CA. Configurable buffer 510 includes a pair of command multiplexers 515 controlled by a programmable register 520. In a single-module configuration, similar to that illustrated in FIG. 2, multiplexers 515 connect command interfaces MCA0 and MCA1 to the respective left- and right-side command busses CA0. In the dual-module configuration, similar to that illustrated in FIG. 3, multiplexers 515 connect command interfaces MCA2 and MCA3 to the respective left- and right-side command busses CA0. Providing the requisite command steering in buffer 510 simplifies the design of memory devices 505. Buffered memory modules provide additional functionality, including to route and buffer commands and data between a memory controller and the memory devices.

Memory devices 505 are width-configurable in this embodiment. In other embodiments buffer 510 can selectively combine fixed or variable-width memory devices to support width configurability. For example, two four-bit-wide memory die can be controlled separately to communicate four-bit-wide data, or together to communicate eight-bit-wide data.

While the present invention has been described in connection with specific embodiments, after reading this disclosure, variations of these embodiments will be apparent to those of ordinary skill in the art. Moreover, some components are shown directly connected to one another while others are shown connected via intermediate components. In each instance the method of interconnection, or “coupling,” establishes some desired electrical communication between two or more circuit nodes, or terminals. Such coupling may often be accomplished using a number of circuit configurations, as will be understood by those of skill in the art. Therefore, the spirit and scope of the appended claims should not be limited to the foregoing description. Only those claims specifically reciting “means for” or “step for” should be construed in the manner required under the sixth paragraph of 35 U.S.C. §112. 

1. (canceled)
 2. A memory controller to control memory devices disposed on a memory module, the memory devices each having a selectable first command port and a selectable second command port, the memory controller comprising: circuitry to configure a first subset of the memory devices to receive first commands via first command ports at each respective memory device in the first subset of the memory devices, and to configure a second subset of the memory devices to receive second commands via second command ports at each respective memory device in the second subset of the memory devices; a first command interface to connect to the first command port of each memory device of the first subset of the memory devices; and a second command interface to connect to the second command port of each memory device of the second subset of the memory devices.
 3. The memory controller of claim 2, each memory device having mode memory to select between the first command port and the second command port, the memory controller to issue a mode command to each of the memory devices to load the mode memories.
 4. The memory controller of claim 3, the memory controller to convey a mode value to the mode memory with the mode command.
 5. The memory controller of claim 4, further comprising data ports to communicate data to the memory devices, the memory controller to convey the mode value to the mode memory over at least one of the data ports.
 6. The memory controller of claim 2, the first command interface to connect to the first command ports via a second module.
 7. The memory controller of claim 6, the second command interface to connect to the second command ports bypassing the second module.
 8. The memory controller of claim 2, the memory controller to control second memory devices disposed on a second memory module, the second memory devices each having a selectable third command port and a selectable second command port.
 9. The memory controller of claim 8, the circuitry to configure a third subset of the memory devices on the second memory module to receive third commands via the third command ports and to configure a fourth subset of the memory devices to receive fourth commands via the fourth command ports.
 10. The memory controller of claim 9, further comprising: a third command interface to connect to the third command port of each memory device of the third subset of the memory devices; and a fourth command interface to connect to the fourth command port of each memory device of the fourth subset of the memory devices.
 11. A method of communicating memory commands and data to memory devices disposed on a memory module, the memory devices each having a first command port adapted to receive the memory commands, a second command port adapted to receive the memory commands, a multiplexer to select only one of the first and second command ports, and mode memory to control the multiplexer to select the one of the first and second command ports, the method comprising: issuing a mode command to each of the memory devices to load the mode memories and control the multiplexers, the mode command causing each of the multiplexers to select the one of the first and second command ports; issuing first commands to the first command port of a first subset of the memory devices disposed on the memory module; and issuing second commands to the second command port of a second subset of the memory devices.
 12. The method of claim 11, wherein the mode memory comprises a mode register on each of the memory devices.
 13. The method of claim 11, further comprising issuing second memory commands and communicating second data to second memory devices disposed on a second memory module.
 14. The method of claim 11, further comprising conveying a mode value to the mode memory with the mode command.
 15. The method of claim 14, further comprising conveying the mode value to the mode memory over at least one data ports.
 16. A memory controller to issue memory commands and communicate data to memory devices disposed on a memory module, the memory devices each having a first command port adapted to receive the memory commands from the memory controller, a second command port adapted to receive the memory commands from the memory controller, a multiplexer to select only one of the first and second command ports, and mode memory to control the multiplexer to select the one of the first and second command ports, the memory controller comprising: a first command interface to connect to the first command port of a first subset of the memory devices disposed on the memory module; a second command interface to connect to the second command port of a second subset of the memory devices; and means for issuing a mode command to each of the memory devices to load the respective mode memories and control the multiplexers.
 17. The memory controller of claim 16, wherein the mode memory comprises a mode register on each of the memory devices.
 18. The memory controller of claim 16, the memory controller further comprising means for issuing second memory commands and communicating second data to second memory devices disposed on a second memory module, the second memory devices each having a third command port and a fourth command port.
 19. The memory controller of claim 18, further comprising: a third command interface to connect to the third command ports of a third subset of the second memory devices disposed on the second memory module; and a fourth command interface to connect to the fourth command ports of a fourth subset of the second memory devices disposed on the second memory module.
 20. The memory controller of claim 16, further comprising means for communicating a mode value and data to the memory devices. 